Four Ways Delegated Work Lands Back On Your Desk

Paul handed the vendor renewal to Natalia on a Monday. Clean handoff, by his account. He explained the contract, forwarded the thread, and told her it was hers.

On Thursday it was back. Not formally. Natalia asked a question he had to answer, then a second one, then forwarded him something to approve, and by Friday afternoon Paul was on a call with the vendor's account manager explaining the renewal terms himself.

Work travels back along specific routes. Four of them show up more than the rest, and each one closes differently.

It came back because you gave the task without the authority

Natalia could negotiate the renewal. She couldn't sign anything, approve a variance, or tell the vendor no. Every one of those hit a wall and bounced to Paul.

​The Center for Creative Leadership frames delegation as handing over authority alongside the work, together with the resources, direction, and support needed to hit the expected result. Drop the authority, and you've assigned homework and kept the decision-making power to yourself.

The tell is easy to spot: the work returns as a question you can answer in eleven seconds. "Are we okay with a 4% uplift?" That's the sound of a decision you never handed over.

Close it by naming the ceiling out loud at handoff. Natalia can approve up to 5% and a twelve-month term without asking. Above that, she comes back. Write the number in the handoff message so the vendor's account manager hears it from her, not from you.

It came back because the context lives in your head

Three years ago Paul's predecessor accepted a bad SLA on this contract, and the vendor has been quietly trading on it since. Paul knows that. Natalia doesn't.

So when the account manager said, "We've always done it this way," Natalia had no way to test the claim. She did the only sensible thing available to her and asked the person who did know.

Gary Yukl and Ping Ping Fu surveyed managers and their reports and found more delegation went to people who were competent, shared the manager's task objectives, and had worked with the manager longer. Shared objectives sit right in the middle of that list, and shared objectives are made of context. Handing someone a task while keeping the history is what turns a capable person into a messenger.

Close it with five minutes of history at handoff. What was tried before, what went wrong, and who has an interest in the outcome. Natalia doesn't need your files. She needs the three things she'd otherwise learn by walking into them.

It came back because you volunteered for the rescue

Paul saw Natalia struggling on the Wednesday call and said he'd sit on the Thursday one, just to help.

William Oncken and Donald Wass named this in 1974, and it hasn't aged. Their account of upward-travelling work turns on a single sentence a manager says with the best intentions: "Let me think about that and get back to you." The task changes owner in that moment, and the manager is now the one being chased for an update.

Rescue is the version that feels most like good management. You're not taking it back. You're helping. Then you're on the call, then you're on the follow-up, then the vendor is emailing you directly and Natalia has been demoted to cc.

Close it by helping in a form that can't turn into ownership. Sit in on the call with your camera on and your mouth shut. Debrief for ten minutes afterwards. If you must speak, say the person's name and hand it back: "Natalia's got the numbers on that one."

It came back because you moved the deadline

Natalia was going to miss Friday. Paul moved it to the following Wednesday, which felt generous and cost nothing.

It cost something. The deadline became a thing he owned, negotiable on request, and the next slip arrived faster.

Roger Buehler, Dale Griffin, and Michael Ross measured how badly people forecast their own work. Psychology students estimating their honors theses predicted 33.9 days on average and took 55.5. Their worst-case guesses still landed short of what actually happened. Optimism about your own timeline is the default setting, and it doesn't respond to being told about itself.

So Natalia's Friday was probably never Friday. The fix lives before the slip, not after it.

Close it by making the checkpoint earlier than the deadline. Agree Wednesday as the moment you look at progress together, three days before Friday matters. A missed Wednesday checkpoint is a conversation. A missed Friday deadline is a rescue.

What to do with all four this week

Pick the piece of work that has bounced back to you most recently and run it through the four paths. One of them will be obviously the one. It usually is.

Then rewrite the handoff message. Four lines, no meeting required: what the outcome looks like, what this person can decide without you, the history they'd otherwise discover the hard way, and the date you'll look at it together before the deadline.

Send it and then do the hard part, which is being unavailable for the rescue. When the question arrives and you can answer it in eleven seconds, answer with a question instead. "What would you do if I were out this week?" Nine times in ten they already know.

Paul's next handoff was the office move, which was messier than the renewal. He gave Natalia a budget ceiling, twenty minutes of history about the landlord, and a checkpoint on the Tuesday. She came to him twice in six weeks, both times with a decision above her ceiling, which is exactly what a ceiling is for.

He wasn't on any of the calls.